Identification and provision of reported aspects that are relevant with respect to achievement of target outcomes

ABSTRACT

A computationally implemented method includes, but is not limited to: identifying, in response to reception of one or more solicitations, one or more relevant reported aspects associated with one or more source users that are relevant to achieving one or more target outcomes, the identification of the one or more relevant reported aspects being based, at least in part, on relevancy of the one or more relevant reported aspects with respect to achieving the one or more target outcomes; and providing the one or more relevant reported aspects. In addition to the foregoing, other method aspects are described in the claims, drawings, and text forming a part of the present disclosure.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Related Applications”) (e.g., claims earliestavailable priority dates for other than provisional patent applicationsor claims benefits under 35 USC §119(e) for provisional patentapplications, for any and all parent, grandparent, great-grandparent,etc. applications of the Related Application(s)). All subject matter ofthe Related Applications and of any and all parent, grandparent,great-grandparent, etc. applications of the Related Applications isincorporated herein by reference to the extent such subject matter isnot inconsistent herewith.

RELATED APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,489, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 3Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/584,653, entitled PERSONALIZED PLAN DEVELOPMENT,naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y.Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 8Sep. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,018, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 29 Sep. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/587,127, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON OUTCOME IDENTIFICATION, naming Shawn P. Firminger; Jason Garms;Roderick A. Hyde; Edward K. Y. Jung; Chris D. Karkanias; Eric C.Leuthardt; Royce A. Levien; Richard T. Lord; Robert W. Lord; Mark A.Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle;Lowell L. Wood, Jr. as inventors, filed 30 Sep. 2009, which is currentlyco-pending, or is an application of which a currently co-pendingapplication is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,027, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 29 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,039, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON ONE OR MORE REPORTED ASPECTS' ASSOCIATION WITH ONE OR MORESOURCE USERS, naming Shawn P. Firminger; Jason Garms; Roderick A. Hyde;Edward K. Y. Jung; Chris D. Karkanias; Eric C. Leuthardt; Royce A.Levien; Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D.Rinaldo, Jr.; Clarence T. Tegreene; Kristin M. Tolle; Lowell L. Wood,Jr. as inventors, filed 30 Oct. 2009, which is currently co-pending, oris an application of which a currently co-pending application isentitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 12/590,600, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 10Nov. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. ______, entitled PERSONALIZED PLAN DEVELOPMENTBASED ON IDENTIFICATION OF ONE OR MORE RELEVANT REPORTED ASPECTS, namingShawn P. Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung;Chris D. Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord;Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T.Tegreene; Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 12Nov. 2009, which is currently co-pending, or is an application of whicha currently co-pending application is entitled to the benefit of thefiling date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. ______, entitled DEVELOPMENT OF PERSONALIZED PLANSBASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 17 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. ______, entitled DEVELOPMENT OF PERSONALIZED PLANSBASED ON ACQUISITION OF RELEVANT REPORTED ASPECTS, naming Shawn P.Firminger; Jason Garms; Roderick A. Hyde; Edward K. Y. Jung; Chris D.Karkanias; Eric C. Leuthardt; Royce A. Levien; Richard T. Lord; RobertW. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Clarence T. Tegreene;Kristin M. Tolle; Lowell L. Wood, Jr. as inventors, filed 18 Nov. 2009,which is currently co-pending, or is an application of which a currentlyco-pending application is entitled to the benefit of the filing date.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation or continuation-in-part. Stephen G. Kunin, Benefit ofPrior-Filed Application, USPTO Official Gazette Mar. 18, 2003, availableat http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm.The present Applicant Entity (hereinafter “Applicant”) has providedabove a specific reference to the application(s) from which priority isbeing claimed as recited by statute. Applicant understands that thestatute is unambiguous in its specific reference language and does notrequire either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant is designating the present applicationas a continuation-in-part of its parent applications as set forth above,but expressly points out that such designations are not to be construedin any way as any type of commentary and/or admission as to whether ornot the present application contains any new matter in addition to thematter of its parent application(s).

SUMMARY

A computationally implemented method includes, but is not limited toidentifying, in response to reception of one or more solicitations, oneor more relevant reported aspects associated with one or more sourceusers that are relevant to achieving one or more target outcomes, theidentification of the one or more relevant reported aspects being based,at least in part, on relevancy of the one or more relevant reportedaspects with respect to achieving the one or more target outcomes; andproviding the one or more relevant reported aspects. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the present disclosure.

In one or more various aspects, related systems include but are notlimited to circuitry and/or programming for effecting theherein-referenced method aspects; the circuitry and/or programming canbe virtually any combination of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

A computationally implemented system includes, but is not limited to:means for identifying, in response to reception of one or moresolicitations, one or more relevant reported aspects associated with oneor more source users that are relevant to achieving one or more targetoutcomes, the identification of the one or more relevant reportedaspects being based, at least in part, on relevancy of the one or morerelevant reported aspects with respect to achieving the one or moretarget outcomes; and means for providing the one or more relevantreported aspects. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

A computationally implemented system includes, but is not limited to:circuitry for identifying, in response to reception of one or moresolicitations, one or more relevant reported aspects associated with oneor more source users that are relevant to achieving one or more targetoutcomes, the identification of the one or more relevant reportedaspects being based, at least in part, on relevancy of the one or morerelevant reported aspects with respect to achieving the one or moretarget outcomes; and circuitry for providing the one or more relevantreported aspects. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

A computer program product including a signal-bearing medium bearing oneor more instructions for identifying, in response to reception of one ormore solicitations, one or more relevant reported aspects associatedwith one or more source users that are relevant to achieving one or moretarget outcomes, the identification of the one or more relevant reportedaspects being based, at least in part, on relevancy of the one or morerelevant reported aspects with respect to achieving the one or moretarget outcomes; and one or more instructions for providing the one ormore relevant reported aspects. In addition to the foregoing, othercomputer program product aspects are described in the claims, drawings,and text forming a part of the present disclosure.

A method for providing relevant reported aspects that are relevant toachieving one or more target outcomes, the method includes identifying,using a processor one or more relevant reported aspects associated withone or more source users that are relevant to achieving one or moretarget outcomes, the identification of the one or more relevant reportedaspects in response to reception of one or more solicitations and beingbased, at least in part, on relevancy of the one or more relevantreported aspects with respect to achieving the one or more targetoutcomes; and providing the one or more relevant reported aspects.

The foregoing summary is illustrative only and is not intended to be inany way limiting. In addition to the illustrative aspects, embodiments,and features described above, further aspects, embodiments, and featureswill become apparent by reference to the drawings and the followingdetailed description.

BRIEF DESCRIPTION OF THE FIGURES

FIGS. 1 a and 1 b show a high-level block diagram of a Computing Device10 operating in a network environment.

FIG. 2 a shows another perspective of the Relevant Reported AspectIdentification Module 102 of the Computing Device 10 of FIG. 1 b.

FIG. 2 b shows another perspective of the Relevant Reported AspectProviding Module 104 of the Computing Device 10 of FIG. 1 b.

FIG. 2 c shows one perspective of one of the Sensing Devices 40 of theenvironment of FIGS. 1 a and 1 b.

FIG. 3 is a high-level logic flowchart of a process.

FIG. 4 a is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 b is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 c is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 d is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 e is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 f is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 g is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 4 h is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect identifyingoperation 302 of FIG. 3.

FIG. 5 a is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 304 of FIG. 3.

FIG. 5 b is a high-level logic flowchart of a process depictingalternate implementations of the relevant reported aspect providingoperation 304 of FIG. 3.

FIG. 6 is another high-level block diagram showing one implementation ofthe computing device 10 of FIG. 1 b.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. The illustrative embodiments described in thedetailed description, drawings, and claims are not meant to be limiting.Other embodiments may be utilized, and other changes may be made,without departing from the spirit or scope of the subject matterpresented here.

A recent trend that has enjoyed explosive popularity in thecomputing/communication field is to electronically record one's dailyactivities, behaviors, thoughts, beliefs, traits, physical or mentalstates, physical characteristics, and other aspects of the person'severyday life onto an open journal. One place where such open journalsare maintained is at social networking sites commonly known as “blogs”where one or more users may report or post every aspect of their dailylives. In brief, an “aspect,” as will be referred to herein, may be inreference to any act, behavior, characteristic, user state or status,belief, and so forth, that may be associated with a user (e.g., a personincluding, for example, a network user such as a blogger or a socialnetworking user). The process of reporting or posting blog entries iscommonly referred to as “blogging.” A newer type of blogging that hasbecome very popular in recent times is microblogging, otherwise known as“twittering” or “tweeting.” In microblogging, each of the microblogsthat are posted are typically relatively short posts or entries, usuallynot more than 140 characters long.

Other types of social networking sites may also allow users to maintainopen journals and to allow users to easily update their personalinformation in real time. Such updates are typically made via, forexample, social networking status reports otherwise known simply as“status reports.” These social networking sites allow a user to reportor post for others to view the latest status or other aspects related tothe user.

Another recent tread in social networking is to employ one or moresensors to detect and report on a wide variety of user aspects (i.e.,aspects of a user). Examples of sensors that may be used for suchpurposes vary widely, ranging from well-known devices that can detectand report on various physiological parameters such as heart rate orblood pressure, to sensors that can detect certain user behaviors oractivities such as toilet usage. Although a wealth of personalinformation provided through log entries (e.g., microblogs, statusreports, sensor data, and so forth) are now available through thesesocial networking sites, it is only recently has there been any effortto exploit such potentially useful data. As blogs, microblogs, andvarious social networking sites become increasingly popular, personaldata collected through such means may be spread across multiple networksites making it even more difficult to exploit such potentially usefuldata.

In various embodiments, methods, systems, circuitry, and computerprogram products are provided for providing one or more reported aspectsof one or more users that are relevant for achieving one or more targetoutcomes. More particularly, the methods, systems, circuitry, andcomputer program products may be designed to identify selectively, inresponse to reception of one or more solicitations, one or more relevantreported aspects associated with one or more “source users” that arerelevant to achieving one or more target outcomes, the selectiveidentification of the one or more relevant reported aspects being based,at least in part, on relevancy of the one or more relevant reportedaspects with respect to achieving the one or more target outcomes.

Based on the identification of the one or more relevant reportedaspects, the one or more identified relevant reported aspects may thenbe provided. In some cases, the providing of the one or more relevantreported aspects may involve transmission of, displaying of, allowingaccess to, and/or distribution of such data to one or morecomputing/communication devices such as network devices. In variousembodiments, the methods, systems, circuitry, and computer programproducts may be implemented by a variety of computing/communicationdevices including, for example, a network device such as a server (e.g.,network servers) or a local client device.

In various embodiments, the one or more relevant reported aspects thatare provided by the methods, systems, circuitry, and computer programproducts may be used directly by an end user in order to achieve the oneor more target outcomes when the one or more relevant reported aspectsare emulated by the end user. Alternatively, the one or more relevantreported aspects that are provided may be used in order to develop oneor more templates and/or one or more personalized plans, which may thenbe used by an end user in order to achieve the one or more targetoutcomes. A “template” is a generic plan designed to facilitate theachievement of one or more target outcomes when one or more emulatableaspects included in the template are emulated. The one or moreemulatable aspects that may be included in the template may correspondto the one or more relevant reported aspects that were provided and thatare relevant for achieving the one or more target outcomes.

In contrast, a “personalized plan” may merely be a template that haspersonalized for a particular end user. For example, by taking a generictemplate and modifying the generic template (e.g., modifying orreplacing the emulatable aspects that may be included in the generictemplate) such that the modified generic template (e.g., personalizedplan) meets or satisfies logistical or physical limitations of the enduser. An example of a personalized plan (or a template) is apersonalized plan (or a template) that was developed based on relevantreported aspects of a source user that facilitates an end user toachieve a desired outcome such as weight loss or getting a high score onthe scholastic aptitude test (SAT).

Such a personalized plan (or template) may be embodied by a schedule ofactivities (e.g., emulatable aspects) that an end user may need toemulate in order to achieve the target outcome. For example, if thepersonalized plan is designed to facilitate an end user to lose weight,it may include a schedule of when and what activities (e.g., go joggingfor 30 minutes on day 1, go swimming for 40 minutes on day 2, and soforth) the end user may need to execute in order to achieve the weightloss. Similarly, if the personalized plan is designed to facilitate anend user to achieve a high score for the SAT, the personalized plan maybe a schedule of when and what activities (e.g., read a particular bookon day 1, work on math problems from a particular math book on day 2,and so forth) the end user may need to execute in order to achieve thehigh test score for the SAT.

In order to facilitate understanding of the various concepts to bedescribed herein, an introduction to the meaning of certain words andphrases to be used in the following discussion is now provided. Inbrief, and as will be further described herein, an “aspect” may be anyoccurrence of any behavior, act, belief, characteristic, state, or anyother facet associated with a source user or a group of source users. A“source user” may be any person, such as a microblogger, who may be thebasis for one or more reported aspects. Note that a source user may notnecessarily have to be the source for the one or more reported aspectsthat are related to the source user since reported aspects that areassociated with a particular source user may be provided by other sourceusers or by sensing devices. Note that in some cases, a template or apersonalized plan does not have to be a schedule of activities, but maymerely be a collection of one or more emulatable aspects. For example, atemplate may be developed (based on relevant reported aspects) forachieving lower blood pressure that may indicate a single emulatableaspect (e.g., be spiritual or religious all the time).

A “reported aspect” may be any aspect associated with a source user thathas been reported by various means (e.g., microblog entries, statusreports, sensing device entries, and so forth). A “relevant reportedaspect” is a reported aspect that is relevant to achieving one or moretarget outcomes (e.g., sought-after goals or desired outcomes). In someembodiments, what constitutes “relevant” with respect to achieving oneor more target outcomes may depend on one or more “relevancy factors”that may be considered in determining, for example, whether a reportedaspect is relevant to achieving one or more target outcomes as will befurther described herein. Note that references in the following to“reported aspects” and “relevant reported aspects” will actually be inreference to data that indicate such information (e.g., data thatindicate reported aspects and data that indicate relevant reportedaspects) unless indicated otherwise.

In some embodiments, a reported aspect may have been originally reportedvia log entry such as a blog or microblog entry, a status report, ajournal entry, a sensing device entry, or other types of entry. Such alog entry may be provided by the source user that the reported aspect isassociated with, by another source user, by a third party (e.g., networkservice provider), or by a sensing device that can detect the aspectbeing reported.

A “target outcome” may be any type of desirable goal or result that maybe sought by, for example, an end user. Examples of target outcomesinclude, for example, health-related outcomes such as weight loss orimproved cardiovascular conditioning, athletic outcomes such asdeveloping a particular athletic skill including being able to pitch acurve ball or achieving a particular golf handicap, physiologicaloutcomes such as reduced blood pressure or blood glucose levels, socialoutcomes such as obtaining membership into an elite social club orattaining a particular social status, mental state outcomes such asachieving certain level of calmness or happiness, interpersonal orrelational outcomes such as having lots of friends or developing skillto make friends, employment outcomes such as being promoted ordeveloping certain work skills, academic or intellectual outcomes, andso forth.

An “end user” may be any person who is a direct or indirect beneficiaryof one or more relevant reported aspects that may be provided and thatare relevant to achieving one or more target outcomes. In some cases, anend user may be a direct beneficiary of the one or more relevantreported aspects by, for example, directly using (e.g., emulating) theone or more relevant reported aspects in order to achieve the one ormore target outcomes. Alternatively, an end user may be an indirectbeneficiary of the one or more relevant reported aspects by being thebeneficiary of a template or a personalized plan developed based on theone or more relevant reported aspects.

As briefly described above, a “source user” may be any person who may bethe basis for one or more reported aspects. Note that although in mostcases, a source user will be an actual (real) person who may be thebasis for one or more reported aspects, in other cases, however, asource user may be a fictional person such as a composite of multiple“actual” source users. For example, reported aspects indicating actualaspects of a plurality of actual source users may be compiled andprocessed (e.g., normalized or averaged out) in order to create afictional source user.

Turning now to FIGS. 1 a, and 1 b illustrating an example environment100 in which the methods, systems, circuitry, and computer programproducts in accordance with various embodiments may be implemented by acomputing device 10. In particular, the methods, systems, circuitry, andcomputer program products may be implemented at any network deviceincluding at a peer-to-peer network component device. In variousembodiments, the computing device 10 may be a server such as one of theone or more network servers 60 illustrated in FIG. 1 a. Alternatively,the computing device 10 may be a source user device such as one of thelocal source user devices 20* illustrated in FIG. 1 a. In still otherembodiments, the computing device 10 may be an end user device such asone of the local end user device 30* illustrated in FIG. 1 a. Note thatin the following, “*” represents a wildcard. Thus, references in thefollowing description to, for example, “a source user 2*” may be inreference to a source user 2 a, a source user 2 b, and so forth.

Note that for ease of understanding and explanation, the computingdevice 10 of the exemplary environment 100 of FIGS. 1 a and 1 b will begenerally described in the following discussion as being a server (e.g.,server embodiment) rather than an end user device or a source userdevice. Further, although the following discussion related to theexemplary environment 100 of FIG. 1 a and 1 b assumes that the computingdevice 10 is a server, the following discussion will, for the most part,be applicable even if the computing device 10 were an end user device(e.g., local end user device 30*) or a source user device (e.g., localsource user device 20*) with certain obvious exceptions (e.g., if thecomputing device 10 is an end user device or a source user device ratherthan a server, the computing device 10 may communicate with an end user4 or a source user 2* directly through a user interface 120 rather thanindirectly through a wireless network and/or wired network 50 as may bethe case when the computing device 10 is a server). In some embodiments,the computing device 10 may operate via a web 1.0 or web 2.0 construct.

Referring back to FIGS. 1 a and 1 b, and as previously indicated, thecomputing device 10 may be a network device such as a server (e.g.,network server 60) that is designed to communicate with other networkdevices. For example, the computing device 10 may communicate with oneor more source users 2*(e.g., source user 2 a, source user 2 b, and soforth) through one or more local source user devices 20*(e.g., localsource user device 20 a, local source user device 20 b, and so forth),with one or more end users 4*(e.g., end user 4 a, end user 4 b, and soforth) through one or more local end user devices 30*(e.g., local enduser device 30 a, local end user device 30 b, and so forth), with one ormore sensing devices 40, with one or more network servers 60, and/orwith one or more third parties 6 (e.g., one or more content providers,one or more network service providers, and/or one or more other parties)via a wireless network and/or wired network 50. In variousimplementations, the wireless and/or wired network 50 may include atleast one of a local area network (LAN), a wireless local area network(WLAN), personal area network (PAN), Worldwide Interoperability forMicrowave Access (WiMAX), public switched telephone network (PTSN),general packet radio service (GPRS), cellular networks, and/or othertypes of wireless and/or wired networks 50.

In various embodiments, the computing device 10 may be designed to,among other things, identify (e.g., selectively identify, locate, find,search, distinguish, and so forth) one or more relevant reported aspects14 associated with one or more source users 2* that are relevant toachieving one or more target outcomes, the identification of the one ormore relevant reported aspects 14 being based, at least in part, onrelevancy of the one or more relevant reported aspects 14 with respectto achieving the one or more target outcomes. The identification of theone or more relevant reported aspects 14 may, in some cases, be inresponse to reception of one or more solicitations 13 from one or moreend users 4*(e.g., via one or more local end user devices 30*), from oneor more source users 2*(e.g., via one or more local source user devices20*), from one or more network servers 60, or from other parties (e.g.,one or more third parties 6). Note that in embodiments where thecomputing device 10 is an end user device or a source user device, theone or more solicitations 13 may be directly received from an end user4* or a source user 2* via a user interface 120.

In various embodiments, the identification of the one or more relevantreported aspects 14 may be by identifying the one or more relevantreported aspects 14 from a plurality of reported aspects 15, which may,in some embodiments, be stored in memory 116. The plurality of reportedaspects 15 may include both relevant reported aspects 14 that arerelevant to achieving one or more target outcomes, and non-relevantreported aspects 16 that are not relevant to achieving the one or moretarget outcomes. In some implementations, the plurality of reportedaspects 15 may be associated with a single source user 2*. In otherimplementations, however, the plurality of reported aspects 15 may beassociated with a plurality of source users 2*.

The plurality of reported aspects 15, which may be associated with oneor more source users 2*, may be acquired from a variety of differentsources. For example, in some implementations, one or more of theplurality of reported aspects 15 may be acquired from one or more localsource user devices 20*, from one or more network servers 60, from oneor more sensing devices 40, and/or one or more third parties 6.

Note that in embodiments where the computing device 10 is a source userdevice, one or more of the plurality of reported aspects 15 may beacquired directly from one or more sensing devices 40 or directly from asource user 2* via a user interface 120. Further, in embodiments wherethe computing device 10 is a source user device, the computing device 10may include one or more integrated sensors 240 that may be employed inorder to directly sense or detect one or more aspects associated with asource user 2*. As will be further described, a sensor 240 may be anytype of sensor including, for example, sensors that can sense variousphysical characteristics of a source user 2* (e.g., heart rate sensor orblood pressure sensor), sensors that can sense activities of a sourceuser 2*(e.g., a pedometer), sensors that can sense environmentconditions (e.g., air quality sensors), sensors that can sense thelocation of a source user 2*(e.g., global positioning system or GPS),and so forth.

In any event, after identifying the one or more relevant reportedaspects 14, the computing device 10, may be configured to, among otherthings, provide the one or more relevant reported aspects 14 to one ormore entities. In this context, the providing of the one or morerelevant reported aspects 14 may involve transmitting, via the wirelessnetwork and/or the wired network 50, the one or more relevant reportedaspects 14 to one or more network entities such as local source userdevices 20*, network servers 60, local end user devices 30*, and/orthird parties 6. The one or more relevant reported aspects 14 may alsobe provided by displaying or indicating the one or more relevantreported aspects 14 through a user interface 120 (e.g., a displaymonitor and/or speakers) in embodiments where, for example, thecomputing device 10 is a source user device or an end user device.

As briefly described earlier, in some implementations, the operation toidentify the one or more relevant reported aspects 14 by the computingdevice 10 may be in response to the computing device 10 receiving, viathe wireless network and/or the wired network 50, one or moresolicitations 13 from, for example, one or more end users 4* (e.g., viaone or more local end user devices 30*), from one or more source users2*(e.g., via one or more local source user devices 20*), from one ormore network servers 60, or from one or more third parties 6 (e.g., anetwork service provider, a content provider, and so forth). The one ormore solicitations 13 may be, in various implementations, one or morerequests, queries, and so forth. In some embodiments, the one or moresolicitations 13 may indicate at least one or more target outcomes. Inother embodiments, however, the one or more solicitations 13 mayindicate one or more source users 2* who have achieved the one or moretarget outcomes. In embodiments where the computing device 10 is asource user device or an end user device, the one or more solicitations13 may be received through the user interface 120.

The computing device 10 as previously indicated may be a server (e.g.,one of the one or more network servers 60) that may be located at asingle network site, located across multiple network sites, or may be aconglomeration of servers located at multiple network sites. Inembodiments in which the computing device 10 is a source user device(e.g., local source user device 20*) or an end user device (e.g., localend user device 30*) rather than a network server, the computing device10 may be any one of a wide range of mobile or stationarycomputing/communication devices including, for example, a laptop, adesktop, a workstation, a cellular telephone, a personal digitalassistant (PDA), a Smartphone, a web tablet such as a Netbook, and soforth.

With respect to the one or more sensing devices 40 of the exemplaryenvironment 100 of FIGS. 1 a and 1 b, the one or more sensing devices 40may communicate with the wireless network and/or the wired network 50directly or indirectly via the one or more local source user devices20*. As will be further described herein with respect to FIG. 2 c, eachof the one or more sensing devices 40 (see FIG. 2 c) may include one ormore sensors 240, a network interface 242, and/or a memory 244. The oneor more sensors 240 may be designed to detect or sense one or moreaspects associated with one or more source users 2*.

Examples of sensors 240 include, for example, devices that can detectphysical or physiological characteristics of one or more source users2*, devices that can detect activities of the one or more source users2*, devices that can detect external events (e.g., environmentalconditions including the weather, pollution levels, performance of thestock market, and so forth), image capturing device such as a digitalcamera or camcorder, and/or devices that can detect the location of theone or more source users 2* such as a global positioning system or GPS.Examples of devices that can detect physical or physiologicalcharacteristics include, for example, a heart rate monitor, a bloodpressure sensor, a glucose sensor, and so forth. Examples of devicesthat can detect activities of the one or more source users 2* including,for example, a pedometer, a toilet monitoring system (e.g., to monitorbowel movements), exercise machine sensors, an accelerometer to measurea person's movements which may indicate specific activities, and soforth.

Each of the one or more local source user devices 20* and each of theone or more local end user devices 30*(as well as the computing device10 in embodiments in which the computing device 10 is an end user deviceor a source user device) may be any one of a variety ofcomputing/communication devices including, for example, a cellularphone, a personal digital assistant (PDA), a laptop, a desktop, or othertypes of computing/communication devices. In some embodiments, the oneor more local source user devices 20* and/or the one or more local enduser devices 30*(as well as the computing device 10 in some embodiments)may be a handheld device such as a cellular telephone, a Smartphone, aMobile Internet Device (MID), an Ultra Mobile Personal Computer (UMPC),a convergent device such as a personal digital assistant (PDA), and soforth. Alternatively, such local client devices (e.g., local source userdevice 20* and/or local end user device 30*) may be a laptop, a desktop,a workstation, a web tablet such as a Netbook, or other types of devicesthat may not be a handheld device in various alternativeimplementations.

The computing device 10 as illustrated in FIG. 1 b may include a varietyof modules, sub-modules, and various other components. As shown, thecomputing device 10 may include at least a relevant reported aspectidentification module 102 (which may further include one or moresub-modules as illustrated in FIG. 2 a) and a relevant reported aspectproviding module 104 (which may further include one or more sub-modulesas illustrated in FIG. 2 b). In various embodiments, the computingdevice 10 may further include a memory 116 (which may store a pluralityof reported aspects 15 that may further include one or more relevantreported aspects 14 and one or more non-relevant reported aspects 16,one or more end user relevancy indications 142, one or more source userrelevancy indications 144, one or more third party source relevancyindications 145, one or more predefined time increment indications 146,and/or one or more applications 140), a network interface 118 (e.g.,network interface card or NIC), a user interface 120, a socialnetworking entry reception module 110 (which may further include a blogentry reception module 111 and/or a status report reception module 112),a journal entry reception module 114, a sensor data reception module115, and/or a solicitation reception module 122 that is designed toreceive one or more solicitations 13 via, for example, a wirelessnetwork and/or wired network 50 or via user interface 120. Inembodiments where the computing device 10 is a source user device, thecomputing device 10 may include one or more integrated sensors 240 thatare designed to sense or detect one or more aspects associated with oneor more source users 2*.

Referring to the relevant reported aspect identification module 102, therelevant reported aspect identification module 102 may be configured to,among other things, identify one or more relevant reported aspects 14based, at least in part, on relevancy of the one or more relevantreported aspects 14 with respect to achievement of one or more targetoutcomes, the one or more relevant reported aspects 14 to be identifiedbeing associated with one or more source users 2* and being relevant toachieving the one or more target outcomes, and the identification of theone or more relevant reported aspects being in response to reception ofone or more solicitations 13. In contrast, the relevant reported aspectproviding module 104 may be configured to, among other things, providethe identified one or more relevant reported aspects 14.

The memory 116 may be designed to store various data including aplurality of reported aspects 15 associated with one or more source user2*. The plurality of reported aspects 15 stored in the memory 116 mayinclude both relevant reported aspects 14 that are relevant to achievingone or more target outcomes and non-relevant reported aspects 16 thatmay not be relevant to achieving any of the one or more target outcomes.Other types of data may be stored in the memory 116 in variousimplementations including, for example, one or more end user relevancyindications 142 (e.g., one or more indications that indicate the typesof reported aspects that an end user 4 has an interest in or believes isrelevant to achieving one or more target outcomes) and/or one or moresource user relevancy indications 144 (e.g., one or more indicationsprovided by a source user 2* that indicate at least which types ofreported aspects are relevant to achieving one or more target outcomes).

In some cases, the memory 116 may also include, for example, one or morethird party source relevancy indications 145 (e.g., one or moreindications provided by one or more third party sources such as one ormore third parties 6 that indicate at least which types of reportedaspects are relevant to achieving one or more target outcomes), one ormore predefined time increment indications 146 (e.g., one or moreindications that indicate at least one time increment, such as a timeinterval or window, that may be considered in order to determinewhether, for example, a reported aspect is relevant for achieving atarget outcome if the reported aspect indicate an aspect that occurredwithin the time increment from an occurrence of the target outcome assuccessfully achieved by, for example, a source user 2*), and/or one ormore applications 140 (e.g., a text messaging application, an instantmessaging application, an email application, a social networkingapplication, a voice recognition system, a Web 1.0 application, and/orWeb 2.0 application to facilitate in communicating via, for example, theWorld Wide Web). In various implementations, the memory 116 may compriseof one or more of a mass storage device, a read-only memory (ROM), aprogrammable read-only memory (PROM), an erasable programmable read-onlymemory (EPROM), a cache memory such as random access memory (RAM), aflash memory, a synchronous random access memory (SRAM), a dynamicrandom access memory (DRAM), and/or other types of memory devices.

The social networking entry reception module 110 may be configured toreceive social networking entries from one or more sources including,for example, from one or more source users 2*, from one or more endusers 4*, from one or more third parties 6, from one or more sensingdevices 40, and/or from one or more network servers 60. The socialnetworking entry reception module 110 may further include a blog entryreception module 111 for receiving blog entries (e.g. microblog entries)and/or a status report reception module 112 for receiving socialnetworking status reports. The journal entry reception module 114 may beconfigured to receive journal entries from, for example, one or moresource users 2*, one or more end users 4*, and/or one or more thirdparties 6 (e.g., a non-user). The sensor data reception module 115 maybe configured to receive sensing data that indicate one or more reportedaspects 15 associated with one or more source users 2* from one or moresensing devices 40 or one or more integrated sensors 240. The userinterface 120 may include one or more of, for example, a displaymonitor, a touchscreen, a keyboard, a keypad, a mouse, an audio systemincluding one or more speakers, a microphone, an image capturing devicesuch as a digital camera, and so forth.

FIG. 2 a illustrates particular implementations of the relevant reportedaspect identification module 102 of the computing device 10 of FIG. 1 b.As illustrated, the relevant reported aspect identification module 102may include, in various implementations, one or more sub-modules. Forexample, in some implementations, the relevant reported aspectidentification module 102 may include a source user associated reportedaspect identification module 202 that is configured to identify the oneor more relevant reported aspects 14 that are associated with one ormore source users 2* and that are relevant to achieving the one or moretarget outcomes by at least identifying one or more reported aspects 15that are associated with the one or more source users 2*, the one ormore source users 2* having achieved the one or more target outcomes.

The source user associated reported aspect identification module 202 mayfurther include a target outcome corresponding reported aspectidentification module 204 and/or an associated source user determinationmodule 206. The target outcome corresponding reported aspectidentification module 204 may be configured to identify the one or morerelevant reported aspects 14 by at least identifying one or morereported aspects 15 that correspond to the one or more target outcomes.In contrast, the associated source user determination module 206 may beconfigured to determine one or more source users 2* who are associatedwith the one or more reported aspects 15 that correspond to the one ormore target outcomes. In doing so, the one or more source users 2* whohave achieved the one or more target outcomes may be identified ordetermined. Based on the determination of the one or more source users2* who have achieved the one or more target outcomes, the relevantreported aspect identification module 102 may identify one or morereported aspects 15 that are associated with the one or more sourceusers 2* who have achieved the target outcomes.

In some implementations, the relevant reported aspect identificationmodule 102 may include a relevancy factor relevant reported aspectidentification module 208 and/or a log entry originated relevantreported aspect identification module 212. In brief, the relevancyfactor relevant reported aspect identification module 208 may beconfigured to identify one or more reported aspects 14 that are relevantfor achieving one or more target outcomes with respect to one or morerelevancy factors (e.g., the one or more reported aspects 14 belongingto a type or types of aspects that are of interest to an end user 4*).In contrast, the log entry originated relevant reported aspectidentification module 212 may be configured to identify the one or morerelevant reported aspects 14 by identifying one or more reported aspects15 that were originally reported through log entries (e.g., microblogentries, status reports, and so forth).

FIG. 2 b illustrates particular implementations of the relevant reportedaspect providing module 104 of FIG. 1 b. The relevant reported aspectproviding module 104, as illustrated, may include one or moresub-modules. For example, in various implementations, the relevantreported aspect providing module 104 may include a network transmissionmodule 220 that is configured to transmit the one or more relevantreported aspects 14 via a wireless network and/or a wired network 50(e.g., via at least one of a wireless network and a wired network 50).In some implementations, the network transmission module 220 may furtherinclude a network device transmission module 222 configured to transmitthe one or more relevant reported aspects 14 to one or more networkdevices (e.g., network servers 60, local source user devices 20*, localend user devices 30, and/or other network devices).

In various implementations, the relevant reported aspect providingmodule 104 may include a link indication providing module 224 that isconfigured to provide one or more indications that links (e.g.,associates) two or more relevant reported aspects 14 together. In someimplementations, development of a template or a personalized plandesigned to achieve one or more target outcomes and that is developedbased on the two or more relevant reported aspects 14 may be facilitatedby indicating the link between the two or more relevant reported aspects14. In some cases, the link indication providing module 224 may furtherinclude a relationship indication providing module 226 configured toprovide one or more indications that indicate one or more relationships(e.g., temporal, specific time, or spatial relationships) between thetwo or more relevant reported aspects 14. Such indications may also beuseful in order to, for example, develop a template or a personalizedplan designed to achieve one or more target outcomes. In particular, byproviding the one or more indications of the one or more relationshipsbetween the two or more relevant reported aspects 14, the development ofa template or a personalized plan (e.g., a template or personalized planthat may be embodied by, for example, a schedule of emulatable aspects)designed to achieve one or more target outcomes may be betterfacilitated (e.g., providing a basis for the relationships between theemulatable aspects that may be included in the template or thepersonalized plan).

Referring now to FIG. 2 c illustrating one of the sensing devices 40 ofFIGS. 1 a and 1 b. The sensing device 40, in various implementations,may include at least one or more sensors 240. The one or more sensors240 that may be included in a sensing device 40 (as well as thecomputing device 10) may be designed to sense or detect one or moreaspects associated with one or more source users 2*. For example, invarious implementations, the one or more sensors 240 may include one ormore devices that can monitor a user's physiological characteristicssuch as blood pressure sensors, heart rate monitors, glucometers (e.g.,blood glucose meter), and so forth.

In some implementations, the one or more sensors 240 may include devicesthat can detect activities of a user (e.g., a source user 2*). Examplesof such devices include, for example, a pedometer, a toilet monitoringsystem (e.g., to monitor bowel movements), exercise machine sensors, anaccelerometer to measure a person's movements which may indicatespecific activities, and so forth. The one or more sensors 240 may alsoinclude, in various implementations, other types of sensor/monitoringdevices such as video or digital camera to provide electronic images of,for example, the one or more target outcomes as displayed by a sourceuser 2*, global positioning system (GPS) to provide location datarelated to a user (e.g., locations of the source user 2*), and so forth.In various implementations, a sensing device 40 may further include anetwork interface 242 and/or a memory 244. The network interface 242 maybe designed to interface with a wireless network and/or a wired network50 while the memory 244 may be designed to store, for example, sensingdata provided by the one or more sensors 240.

Referring back to the computing device 10 of FIG. 1 b, the variousmodules (e.g., the relevant reported aspect identification module 102,the relevant reported aspect providing module 104, and so forth) alongwith their sub-modules included in the computing device 10 may beimplemented using hardware, software, firmware, or any combinationthereof. For example, in some implementations, the relevant reportedaspect identification module 102 and/or the relevant reported aspectproviding module 104 may be implemented with a processor 602 (e.g.,microprocessor, controller, and so forth) executing computer readableinstructions 604 (e.g., computer program product) stored in a storagemedium 606 (e.g., volatile or non-volatile memory) such as asignal-bearing medium as depicted in the computing device 10 of FIG. 6.Alternatively, hardware such as application specific integrated circuit(ASIC) may be employed in order to implement such modules in somealternative implementations.

A more detailed discussion related to the computing device 10 of FIG. 1b will now be provided with respect to the processes and operations tobe described herein. FIG. 3 illustrates an operational flow 300representing example operations related to, among other things,identification (e.g., selective identification) of one or more relevantreported aspects 14 associated with one or more source users 2* that arerelevant to achieving one or more target outcomes, the identification ofthe one or more relevant reported aspects being based, at least in part,on relevancy of the one or more relevant reported aspects 14 withrespect to the achievement of the one or more target outcomes, theidentification being in response to reception of one or moresolicitations 13, and the providing of the one or more relevant reportedaspects 14 that were identified.

In FIG. 3 and in the following figures that include various examples ofoperational flows, discussions and explanations may be provided withrespect to the exemplary environment 100 described above as illustratedin FIGS. 1 a and 1 b, and/or with respect to other examples (e.g., asprovided in FIGS. 2 a, 2 b, and 2 c) and contexts. However, it should beunderstood that the operational flows may be executed in a number ofother environments and contexts, and/or in modified versions of FIGS. 1a, 1 b, 2 a, 2 b, and 2 c. Also, although the various operational flowsare presented in the sequence(s) illustrated, it should be understoodthat the various operations may be performed in other orders other thanthose which are illustrated, or may be performed concurrently.

Further, in FIG. 3 and in the figures to follow thereafter, variousoperations may be depicted in a box-within-a-box manner. Such depictionsmay indicate that an operation in an internal box may comprise anoptional example embodiment of the operational step illustrated in oneor more external boxes. However, it should be understood that internalbox operations may be viewed as independent operations separate from anyassociated external boxes and may be performed in any sequence withrespect to all other illustrated operations, or may be performedconcurrently.

In any event, after a start operation, the operational flow 300 may moveto a relevant reported aspect identifying operation 302 for identifying,in response to reception of one or more solicitations, one or morerelevant reported aspects associated with one or more source users thatare relevant to achieving one or more target outcomes, theidentification of the one or more relevant reported aspects being based,at least in part, on relevancy of the one or more relevant reportedaspects with respect to achieving the one or more target outcomes. Forinstance, and as an illustration, the relevant reported aspectidentification module 102 of the computing device 10 of FIG. 1 bidentifying (e.g., finding, locating, searching, distinguishing, and soforth), in response to reception of one or more solicitations 13 (e.g.,requests, queries, commands, and so forth), one or more relevantreported aspects 14 associated with one or more source users 2* that arerelevant to achieving one or more target outcomes, the identification ofthe one or more relevant reported aspects 14 being based, at least inpart, on relevancy of the one or more relevant reported aspects 14 withrespect to achieving the one or more target outcomes.

Note that in various implementations, the one or more solicitations 13to be received may be for soliciting the one or more relevant reportedaspects 14. Alternatively, the one or more solicitations 13 may be forsoliciting data for developing one or more personalized plans ortemplates that may be designed to facilitate an end user 4* to achievethe one or more target outcomes. In other implementations, the one ormore solicitations 13 may be for soliciting other types of data.

In addition to the relevant reported aspect identifying operation 302,operational flow 300 may also include a relevant reported aspectproviding operation 304 for providing the one or more relevant reportedaspects. For instance, the relevant reported aspect providing module 104of the computing device 10 providing (e.g., transmitting, indicating,displaying, allowing access to, and so forth) the one or more relevantreported aspects 14. As will be further described herein, the relevantreported aspect identifying operation 302 as well as the relevantreported aspect providing operation 304 may be implemented in a numberof different ways in various alternative implementations.

For example, FIGS. 4 a, 4 b, 4 c, 4 d, 4 e, 4 f, 4 g, and 4 h illustratethe various ways that the relevant reported aspect identifying operation302 of FIG. 3 may be implemented in various alternative implementations.In some implementations, for example, the relevant reported aspectidentifying operation 302 of FIG. 3 may include an operation 402 foridentifying, in response to the reception of the one or moresolicitations, the one or more relevant reported aspects from aplurality of reported aspects as depicted in FIG. 4 a. For instance, therelevant reported aspect identification module 102 of the computingdevice 10 of FIG. 1 b identifying, in response to receiving the one ormore solicitations 13 (e.g., as received by the solicitation receptionmodule 122), the one or more relevant reported aspects 14 from aplurality of reported aspects 15.

In some implementations, operation 402 may further include an operation403 for identifying, in response to the reception of the one or moresolicitations, the one or more relevant reported aspects from aplurality of reported aspects that include one or more reported aspectsthat are relevant to achieving the one or more target outcomes and oneor more reported aspects that are not relevant to achieving the one ormore target outcomes as depicted in FIG. 4 a. For instance, the relevantreported aspect identification module 102 of the computing device 10identifying, in response to receiving the one or more solicitations 13,the one or more relevant reported aspects 14 from a plurality ofreported aspects 15 that include one or more reported aspects that arerelevant to achieving the one or more target outcomes (e.g., one or morerelevant reported aspects 14) and one or more reported aspects 16 thatare not relevant to achieving the one or more target outcomes.

In the same or different implementations, the relevant reported aspectidentifying operation 302 of FIG. 3 may include an operation 404 foridentifying the one or more relevant reported aspects in response toreception of one or more solicitations that indicate the one or moresource users, the one or more source users having achieved the one ormore target outcomes as depicted in FIG. 4 a. For instance, the relevantreported aspect identification module 102 of the computing device 10identifying the one or more relevant reported aspects 14 in response toreception of one or more solicitations 13 that indicate the one or moresource users 2*, the one or more source users 2* having achieved the oneor more target outcomes.

In the same or different implementations, the relevant reported aspectidentifying operation 302 may include an operation 405 for identifyingthe one or more relevant reported aspects in response to reception ofone or more solicitations that indicate the one or more target outcomesas depicted in FIG. 4 a. For instance, the relevant reported aspectidentification module 102 of the computing device 10 identifying the oneor more relevant reported aspects 14 in response to reception (e.g.,reception by the solicitation module 122) of one or more solicitations13 that indicate the one or more target outcomes.

In various implementations, operation 405 may include one or moreadditional operations. For example, in some implementations, operation405 may include an operation 406 for identifying the one or morerelevant reported aspects in response to reception of one or moresolicitations that indicate the one or more target outcomes and that donot indicate any of the one or more source users as depicted in FIG. 4a. For instance, the relevant reported aspect identification module 102of the computing device 10 identifying the one or more relevant reportedaspects 14 in response to reception (e.g., reception by the solicitationmodule 122) of one or more solicitations 13 that indicate the one ormore target outcomes and that do not indicate any of the one or moresource users 2*.

In the same or different implementations, operation 405 may include anoperation 407 for identifying the one or more relevant reported aspectsin response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more relevancyfactors as depicted in FIG. 4 a. For instance, the relevant reportedaspect identification module 102 of the computing device 10 identifyingthe one or more relevant reported aspects 14 in response to reception(e.g., reception by the solicitation module 122) of one or moresolicitations 13 that indicate the one or more target outcomes and thatindicate one or more relevancy factors (e.g., bases for determiningwhether a reported aspect is relevant to achieving one or more targetoutcomes).

Operation 407 in turn may further include an operation 408 foridentifying the one or more relevant reported aspects in response toreception of one or more solicitations that indicate the one or moretarget outcomes and that indicate one or more aspect types that are ofinterest to one or more end users, the one or more end users beingbeneficiaries of the providing of the one or more relevant reportedaspects as depicted in FIG. 4 a. For instance, the relevant reportedaspect identification module 102 of the computing device 10 identifyingthe one or more relevant reported aspects 14 in response to reception(e.g., reception by the solicitation module 122) of one or moresolicitations 13 that indicate the one or more target outcomes and thatindicate one or more aspect types (e.g., dietary activities, sleep orrest activities, reading activities, user locations, mental states, andso forth) that are of interest to one or more end users 4*, the one ormore end users 4* being beneficiaries of the providing of the one ormore relevant reported aspects 14.

In the same or different implementations, operation 407 may include anoperation 409 for identifying the one or more relevant reported aspectsin response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more aspect typesindicated by at least one source user as being relevant to theachievement of the one or more target outcomes as depicted in FIG. 4 a.For instance, the relevant reported aspect identification module 102 ofthe computing device 10 identifying the one or more relevant reportedaspects 14 in response to reception (e.g., reception by the solicitationmodule 122) of one or more solicitations 13 that indicate the one ormore target outcomes and that indicate one or more aspect types (e.g.,exercise activities, medication usage, mental attitudes, social oremployment activities, and so forth) indicated by at least one sourceuser 2* as being relevant to the achievement of the one or more targetoutcomes (e.g., losing weight, feeling more alert, reduce pain, increasesexual intimacy activities, and so forth).

In the same or different implementations, operation 407 may include anoperation 410 for identifying the one or more relevant reported aspectsin response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more aspect typesindicated by at least one third party source as being relevant to theachievement of the one or more target outcomes as depicted in FIG. 4 b.For instance, the relevant reported aspect identification module 102 ofthe computing device 10 identifying the one or more relevant reportedaspects 14 in response to reception (e.g., reception by the solicitationmodule 122) of one or more solicitations 13 that indicate the one ormore target outcomes and that indicate one or more aspect typesindicated by at least one third party source 6 as being relevant to theachievement of the one or more target outcomes.

In the same or different implementations, operation 407 may include anoperation 411 for identifying the one or more relevant reported aspectsin response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more predefinedtime increments, the one or more predefined time increments to beconsidered in order to determine relevancy of one or more reportedaspects with respect to achieving the one or more target outcomes asdepicted in FIG. 4 b. For instance, the relevant reported aspectidentification module 102 of the computing device 10 identifying the oneor more relevant reported aspects 14 in response to reception (e.g.,reception by the solicitation module 122) of one or more solicitations13 that indicate the one or more target outcomes and that indicate oneor more predefined time increments, the one or more predefined timeincrements (e.g., one day, one week, three months, one year, five years,and so forth) to be considered in order to determine relevancy of one ormore reported aspects 15 with respect to achieving the one or moretarget outcomes. For example, such predefined time periods may be usedin order to eliminate from consideration those reported aspects 15 thatare associated with one or more source users 2* who have achieved theone or more target outcomes but indicate aspects that occurred remotelyfrom the accomplishment of the one or more target outcomes by the one ormore source users 2*.

In various implementations, the relevant reported aspect identifyingoperation 302 of FIG. 3 may include an operation 412 for identifying theone or more relevant reported aspects by at least identifying one ormore reported aspects that are relevant for achieving the one or moretarget outcomes from a plurality of reported aspects stored in memory asdepicted in FIG. 4 b. For instance, the relevant reported aspectidentification module 102 of the computing device 10 identifying the oneor more relevant reported aspects 14 by at least identifying one or morereported aspects (e.g., relevant reported aspects 14) that are relevantfor achieving the one or more target outcomes from a plurality ofreported aspects 15 stored in memory 116.

In order to identify relevant reported aspects 14 of one or more sourceusers 2* that are relevant for achieving one or more target outcomesfrom, for example, a plurality of reported aspects 15, the relevantreported aspect identifying operation 302 of FIG. 3 may include one ormore operations to identify one or more source users 2* who have beenreported as having successfully achieved the one or more targetoutcomes. For example, in some implementations, the relevant reportedaspect identifying operation 302 may include an operation 413 foridentifying the one or more relevant reported aspects by at leastidentifying one or more reported aspects that are associated with theone or more source users, the one or more source users having achievedthe one or more target outcomes as depicted in FIG. 4 c. For instance,the relevant reported aspect identification module 102 of the computingdevice 10 identifying the one or more relevant reported aspects 14 byhaving the source user associated reported aspect identification module202 (see FIG. 2 a) at least identify one or more reported aspects 15that are associated with the one or more source users 2*, the one ormore source users 2* having achieved the one or more target outcomes.

In order to identify the one or more reported aspects 15 that areassociated with the one or more source users 2* who have achieved theone or more target outcomes, operation 413 may include an operation toidentify those reported aspects 15 that corresponds to the one or moretarget outcomes. For example, in some implementations, operation 413 mayinclude an operation 414 for identifying the one or more relevantreported aspects by at least identifying one or more reported aspectsthat correspond to the one or more target outcomes as depicted in FIG. 4c. For instance, the relevant reported aspect identification module 102of the computing device 10 identifying the one or more relevant reportedaspects 14 by having the target outcome corresponding reported aspectidentification module 204 (see FIG. 2 a) at least identify one or morereported aspects 15 that correspond (e.g., equivalent or substantiallyequivalent) to the one or more target outcomes.

In order to identify the one or more relevant reported aspects 14,operation 414 may include an operation 415 for determining one or moresource users who are associated with the one or more reported aspectsthat correspond to the one or more target outcomes as depicted in FIG. 4c. For instance, the associated source user determination module 206(see FIG. 2 a) of the computing device 10 determining one or more sourceusers 2* who are associated with the one or more reported aspects 15that correspond (e.g., equivalent or substantially equivalent) to theone or more target outcomes.

In some implementations, in order to identify the one or more relevantreported aspects 14 operation 415 may include at least an operation 416for identifying one or more reported aspects that are associated withthe one or more source users determined to be associated with the one ormore reported aspects that corresponds to the one or more targetoutcomes as depicted in FIG. 4 c. For instance, the relevant reportedaspect identification module 102 of the computing device 10 identifyingone or more reported aspects 15 that are associated with the one or moresource users 2* determined to be associated with the one or morereported aspects 15 that corresponds to the one or more target outcomes.

In various implementations, operation 416 may include an operation 417for identifying, from the one or more reported aspects that areassociated with the one or more source users determined to be associatedwith the one or more reported aspects that correspond to the one or moretarget outcomes, one or more reported aspects that are relevant withrespect to one or more relevancy factors as depicted in FIG. 4 c. Forinstance, the relevancy factor relevant reported aspect identificationmodule 208 (see FIG. 2 a) of the computing device 10 identifying, fromthe one or more reported aspects 15 that are associated with the one ormore source users 2* determined to be associated with the one or morereported aspects 15 that correspond to the one or more target outcomes,one or more reported aspects 15 that are relevant with respect to one ormore relevancy factors. Examples of relevancy factors include, forexample, identifying reported aspects 15 that are associated withspecific source users 2* such as those source users 2* who have achievedthe one or more target outcomes and who share certain common traits(e.g., ethnicity, religious beliefs, mental or physical handicaps,common social or employment networking groups, common health or medicalstates, and so forth) with an end user 4*).

The one or more relevancy factors considered in operation 417 may beprovided by a variety of sources. For example, in some implementations,operation 417 may include an operation 418 for identifying the one ormore reported aspects that are relevant with respect to one or morerelevancy factors by identifying one or more reported aspects thatbelong to one or more aspect types that are of interest to an end user,the end user being a beneficiary of the one or more relevant reportedaspects to be provided as depicted in FIG. 4 c. For instance, therelevancy factor relevant reported aspect identification module 208 ofthe computing device 10 identifying the one or more reported aspects 15that are relevant with respect to one or more relevancy factors byidentifying one or more reported aspects that belong to one or moreaspect types (e.g., dietary behaviors, exercise behavior, reportedaspects 14 associated with source users 2* who share a common trait withthe end user 4*, and so forth) that are of interest to an end user 4*,the end user 4* being a beneficiary (e.g., recipient of the one or morerelevant reported aspects 14 or a product, such as a personalized planor a template, that may be generated from the one or more relevantreported aspects 14) of the one or more relevant reported aspects to beprovided.

In the same or different implementations, operation 417 may include anoperation 419 for identifying the one or more reported aspects that arerelevant with respect to one or more relevancy factors by identifyingone or more reported aspects that belong to one or more aspect typesthat have been indicated by at least one source user as being relevantto the achievement of the one or more target outcomes as depicted inFIG. 4 c. For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more reported aspects that are relevant with respect to one or morerelevancy factors by identifying one or more reported aspects 15 thatbelong to one or more aspect types (e.g., mental states, attitudes,spiritual or religious beliefs, conduct, and so forth) that have beenindicated by at least one source user 2* as being relevant to theachievement of the one or more target outcomes (e.g., reduced bloodpressure or reduced stress).

In the same or different implementations, operation 417 may include anoperation 420 for identifying the one or more reported aspects that arerelevant with respect to one or more relevancy factors by identifyingone or more reported aspects that belong to one or more aspect typesthat have been indicated by at least one third party source as beingrelevant to the achievement of the one or more target outcomes asdepicted in FIG. 4 c. For instance, the relevancy factor relevantreported aspect identification module 208 of the computing device 10identifying the one or more reported aspects 15 that are relevant withrespect to one or more relevancy factors by identifying one or morereported aspects that belong to one or more aspect types (e.g., sleepactivities, dietary habits, exercise activities) that have beenindicated by at least one third party source as being relevant to theachievement of the one or more target outcomes (e.g., weight loss).

In the same or different implementations, operation 417 may include anoperation 421 for identifying the one or more reported aspects that arerelevant with respect to one or more relevancy factors by identifyingone or more reported aspects that indicate one or more aspects thatoccurred within one or more predefined time increments, respectively,from one or more occurrences of the one or more reported aspects thatcorrespond to the one or more target outcomes as depicted in FIG. 4 d.For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more reported aspects 15 that are relevant with respect to one ormore relevancy factors by identifying one or more reported aspects 15that indicate one or more aspects that occurred within one or morepredefined time increments (e.g., one day, one week, three months, oneyear, five years, and so forth), respectively, from one or moreoccurrences of the one or more reported aspects 15 that correspond tothe one or more target outcomes.

That is, not all relevant reported aspects 14 that may be relevant withrespect to certain relevancy factors may actually be relevant toachieving the one or more target outcomes if the relevant reportedaspects 14 indicate aspects that, time-wise, occurred remotely fromoccurrence of the one or more target outcomes as successfully achievedby the one or more source users 2* who have been reported as achievingthe one or more target outcomes. For example, reported aspects 15 thatare associated with source users 2* who have achieved the one or moretarget outcomes and that are relevant based on certain relevancy factors(e.g., belong to a type of aspect that is of interest to the end user 4*such as dietary behavior) may, nevertheless, not be relevant toachieving the one or more target outcomes if they occurred well before(or well after) the achievement of the one or more target outcomes(e.g., 20 pounds of weight loss as indicated by one or more reportedaspects 15 that corresponds to the one or more target outcomes) by theone or more source users 2*.

Thus, a reported aspect 15 may, in some cases, be relevant to theachievement of the one or more target outcomes only if it falls withinsome time increment (e.g., “predefined time increment”) from the one ormore occurrences of the one or more reported aspects 15 that correspondto the one or more target outcomes. The length of the predefined timeincrements to be considered in determining relevancy may depend on anumber of factors including how the relevant reported aspects 14 may beused (e.g., to develop personalized plans for achieving targetoutcomes). The predefined time increments, in various implementations,may be provided by an end user 4*, by a source user 2*, or by a thirdparty source (e.g., third party 6).

In various implementations, operation 421 may, in turn, include anoperation 422 for identifying the one or more reported aspects that arerelevant with respect to one or more relevancy factors by identifyingone or more reported aspects that indicate one or more aspects thatoccurred prior to and within one or more predefined time periods,respectively, from one or more occurrences of the one or more reportedaspects that correspond to the one or more target outcomes as depictedby FIG. 4 d. For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more reported aspects 15 that are relevant with respect to one ormore relevancy factors by identifying one or more reported aspects 15that indicate one or more aspects that occurred prior to and within oneor more predefined time periods, respectively, from one or moreoccurrences of the one or more reported aspects that correspond to theone or more target outcomes.

In some implementations, the relevant reported aspect identifyingoperation 302 may include an operation 423 for identifying the one ormore relevant reported aspects including identifying one or morereported aspects that are relevant to achieving the one or more targetoutcomes based on one or more relevancy factors as depicted in FIG. 4 e.For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more relevant reported aspects 14 including identifying one or morereported aspects 15 that are relevant to achieving the one or moretarget outcomes based on one or more relevancy factors (e.g., relevancyfactors as provided by an end user 4*, by a source user 2*, or by athird party source).

In various implementations, operation 423 may include an operation 424for identifying the one or more relevant reported aspects includingidentifying one or more reported aspects associated with one or moresource users who share one or more common traits with an end user, theend user being a beneficiary of the one or more relevant reportedaspects to be provided as depicted in FIG. 4 e. For instance, therelevancy factor relevant reported aspect identification module 208 ofthe computing device 10 identifying the one or more relevant reportedaspects 14 including identifying one or more reported aspects 15associated with one or more source users 2* who share one or more commontraits with an end user 4*, the end user 4* being a beneficiary of theone or more relevant reported aspects 14 to be provided. For theseimplementations, the end user 4* may be a beneficiary as a result of theend user 4* being the recipient of the one or more relevant reportedaspects 14 or recipient of, for example, a personalized plan or templatefor achieving the one or more target outcomes and that was developedbased on the one or more relevant reported aspects 14.

The one or more source users 2* who share one or more common traits withthe end user 4* may have a variety of traits that may be shared with theend user 4* and which may be considered in identifying relevant reportedaspects 14 in various implementations. For example, in someimplementations, operation 424 may include an operation 425 foridentifying the one or more relevant reported aspects includingidentifying one or more reported aspects associated with one or moresource users who are members of one or more social networking groupsthat are associated with the end user as depicted in FIG. 4 e. Forinstance, the relevancy factor relevant reported aspect identificationmodule 208 of the computing device 10 identifying the one or morerelevant reported aspects 14 including identifying one or more reportedaspects 15 associated with one or more source users 2* who are membersof one or more social networking groups that are associated with the enduser 4*.

In the same or different implementations, operation 424 may include anoperation 426 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are members of one or more ethnic or religiousgroups that are associated with the end user as depicted in FIG. 4 e.For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more relevant reported aspects 14 including identifying one or morereported aspects 15 associated with one or more source users 2* who aremembers of one or more ethnic or religious groups (e.g., Hispanic,German, Asian, Christian, Buddhist, and so forth) that are associatedwith the end user 4*.

In the same or different implementations, operation 424 may include anoperation 427 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are members of at least one of a gender and anage group that is associated with the end user as depicted in FIG. 4 e.For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying one ormore relevant reported aspects 14 including identifying one or morereported aspects 15 associated with one or more source users 2* who aremembers of at least one of a gender (e.g., female) and an age (e.g.,over 65 years of age) group that is associated with the end user 4*.

In the same or different implementations, operation 424 may include anoperation 428 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who have one or more physical or mental handicapsthat are associated with the end user as depicted in FIG. 4 e. Forinstance, the relevancy factor relevant reported aspect identificationmodule 208 of the computing device 10 identifying the one or morerelevant reported aspects 14 including identifying one or more reportedaspects 15 associated with one or more source users 2* who have one ormore physical or mental handicaps (e.g., missing a limb, blindness,phobias, bipolar, and so forth) that are associated with the end user4*.

In the same or different implementations, operation 424 may include anoperation 429 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are associated with one or more health ormedical states that are further associated with the end user as depictedin FIG. 4 e. For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 the one or morerelevant reported aspects 14 including identifying one or more reportedaspects 15 associated with one or more source users 2* who areassociated with one or more health or medical states (e.g., havingcancer, a tobacco user, high blood pressure, and so forth) that arefurther associated with the end user 4*.

In the same or different implementations, operation 424 may include anoperation 430 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are associated with one or more intellectual oracademic states that are further associated with the end user asdepicted in FIG. 4 e. For instance, the relevancy factor relevantreported aspect identification module 208 of the computing device 10identifying the one or more relevant reported aspects 14 includingidentifying one or more reported aspects 15 associated with one or moresource users 2* who are associated with one or more intellectual oracademic states that are further associated with the end user 4*.

In the same or different implementations, operation 424 may include anoperation 431 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are associated with one or more social statesthat are further associated with the end user as depicted in FIG. 4 f.For instance, the relevancy factor relevant reported aspectidentification module 208 of the computing device 10 identifying the oneor more relevant reported aspects 14 including identifying one or morereported aspects 15 associated with one or more source users 2* who areassociated with one or more social states (e.g., unmarried) that arefurther associated with the end user 4*.

In the same or different implementations, operation 424 may include anoperation 432 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects associated with oneor more source users who are associated with one or more spiritual,political, or social beliefs that are further associated with the enduser as depicted in FIG. 4 f. For instance, the relevancy factorrelevant reported aspect identification module 208 of the computingdevice 10 identifying the one or more relevant reported aspects 14including identifying one or more reported aspects 15 associated withone or more source users 2* who are associated with one or morespiritual, political, or social beliefs that are further associated withthe end user 4*.

In various implementations, other types of relevancy factors may beconsidered in identifying the one or more relevant reported aspects 14other than relevancy factors that relate to common traits of an end user4* as was the case in operation 424. For example, in someimplementations, operation 423 for identifying the one or more relevantreported aspects 14 based on one or more relevancy factors may includean operation 433 for identifying the one or more relevant reportedaspects including identifying one or more reported aspects that indicateone or more behavior incidences associated with the one or more sourceusers as depicted in FIG. 4 f. For instance, the relevancy factorrelevant reported aspect identification module 208 of the computingdevice 10 identifying the one or more relevant reported aspects 14including identifying one or more reported aspects 15 that indicate oneor more behavior incidences (e.g., exercise or sleep activities)associated with the one or more source users 2*.

Operation 433 may further include, in various implementations, anoperation 434 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore incidences of activities executed by the one or more source usersas depicted in FIG. 4 f. For instance, the relevancy factor relevantreported aspect identification module 208 of the computing device 10identifying the one or more relevant reported aspects 14 includingidentifying one or more reported aspects 15 that indicate one or moreincidences of activities (e.g., dietary activities, social or employmentactivities, leisure activities, and so forth) executed by the one ormore source users 2*.

In the same or different implementations, operation 433 may include anoperation 435 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore user attitudes or conduct associated with the one or more sourceusers as depicted in FIG. 4 f. For instance, the relevancy factorrelevant reported aspect identification module 208 of the computingdevice 10 identifying the one or more relevant reported aspects 14including identifying one or more reported aspects 15 that indicate oneor more user attitudes or conduct (e.g., mannerisms, outlook, approach,demeanor, and so forth) associated with the one or more source users 2*.

In some implementations, operation 423 may include an operation 436 foridentifying the one or more relevant reported aspects includingidentifying one or more reported aspects that indicate one or moreincidences of one or more user beliefs associated with the one or moresource users as depicted in FIG. 4 g. For instance, the relevancy factorrelevant reported aspect identification module 208 of the computingdevice 10 identifying the one or more relevant reported aspects 14including identifying one or more reported aspects 15 that indicate oneor more incidences of one or more user beliefs (e.g., spiritual orreligious beliefs, superstitious beliefs, dietary beliefs, and so forth)associated with the one or more source users 2*.

In the same or different implementations, operation 423 may include anoperation 437 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore incidences of one or more subjective user states associated withthe one or more source users as depicted in FIG. 4 g. For instance, therelevancy factor relevant reported aspect identification module 208 ofthe computing device 10 identifying the one or more relevant reportedaspects 14 including identifying one or more reported aspects 15 thatindicate one or more incidences of one or more subjective user statesassociated with the one or more source users 2*.

A subjective user state may be any state or status associated with asource user 2* that can typically only be indicated by the source user2*. Examples of subjective user states include, for example, subjectiveuser mental states (e.g., sadness, happiness, mental exhaustion,alertness, and so forth), subjective user physical states (e.g., soreback, blurred vision, overall physical exhaustion, and so forth), andsubjective user overall states (e.g., any other subjective user statesthat are neither a subjective user mental state or a subjective userphysical state including, for example, “feeling good,” “feeling bad,”“feeling alive,” and so forth).

In the same or different implementations, operation 423 may include anoperation 438 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore incidences of one or more user physical characteristics associatedwith the one or more source users as depicted in FIG. 4 g. For instance,the relevancy factor relevant reported aspect identification module 208of the computing device 10 identifying the one or more relevant reportedaspects 14 including identifying one or more reported aspects 15 thatindicate one or more incidences of one or more user physicalcharacteristics (e.g., hair color, skin color, overall physical shape,and so forth) associated with the one or more source users 2*.

In the same or different implementations, operation 423 may include anoperation 439 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore incidences of one or more user locations associated with the one ormore source users as depicted in FIG. 4 g. For instance, the relevancyfactor relevant reported aspect identification module 208 of thecomputing device 10 identifying the one or more relevant reportedaspects 14 including identifying one or more reported aspects 15 thatindicate one or more incidences of one or more user locations (e.g.,workplace, home, school, and so forth) associated with the one or moresource users 2*.

In the same or different implementations, operation 423 may include anoperation 440 for identifying the one or more relevant reported aspectsincluding identifying one or more reported aspects that indicate one ormore incidences of external events associated with the one or moresource users as depicted in FIG. 4 g. For instance, the relevancy factorrelevant reported aspect identification module 208 of the computingdevice 10 identifying the one or more relevant reported aspects 14including identifying one or more reported aspects 15 that indicate oneor more incidences of external events (e.g., local weather, performanceof a stock that is of interest to a source user 2*, and so forth)associated with the one or more source users 2*.

The relevant reported aspects identified through the relevant reportedaspect identifying operation 302 of FIG. 3 may have been originallyreported through various alternative means. For example, in someimplementations, the relevant reported aspect identifying operation 302may include an operation 441 for identifying the one or more relevantreported aspects by identifying one or more reported aspects that wereoriginally reported through log entries as depicted in FIG. 4 h. Forinstance, the log entry originated relevant reported aspectidentification module 212 (see FIG. 2 a) of the computing device 10identifying the one or more relevant reported aspects 14 by identifyingone or more reported aspects 15 that were originally reported throughlog entries (e.g., electronic entries that are continuously, regularly,semi-regularly, or randomly entered).

In various implementations, operation 441 may include one or moreadditional operations. For example, in some implementations, operation441 may include an operation 442 identifying the one or more relevantreported aspects by identifying one or more reported aspects that wereoriginally reported through blog entries as depicted in FIG. 4 h. Forinstance, the log entry originated relevant reported aspectidentification module 212 of the computing device 10 identifying the oneor more relevant reported aspects 14 by identifying one or more reportedaspects 15 that were originally reported through blog entries (e.g.,microblog entries).

In the same or different implementations, operation 441 may include anoperation 443 for identifying the one or more relevant reported aspectsby identifying one or more reported aspects that were originallyreported through status reports as depicted in FIG. 4 h. For instance,the log entry originated relevant reported aspect identification module212 of the computing device 10 identifying the one or more relevantreported aspects 14 by identifying one or more reported aspects 15 thatwere originally reported through status reports (e.g., social networkingstatus reports).

In the same or different implementations, operation 441 may include anoperation 444 for identifying the one or more relevant reported aspectsby identifying one or more reported aspects that were originallyreported through journal entries as depicted in FIG. 4 h. For instance,the log entry originated relevant reported aspect identification module212 of the computing device 10 identifying the one or more relevantreported aspects 14 by identifying one or more reported aspects thatwere originally reported through journal entries (e.g., diary entries).

In the same or different implementations, operation 441 may include anoperation 445 for identifying the one or more relevant reported aspectsby identifying one or more reported aspects that were originallyreported through sensing device entries as depicted in FIG. 4 h. Forinstance, the log entry originated relevant reported aspectidentification module 212 of the computing device 10 identifying the oneor more relevant reported aspects 14 by identifying one or more reportedaspects 14 that were originally reported through sensing device entries(e.g., as provided by one or more sensing devices 40 or by sensors 240).

In various implementations, the relevant reported aspect identifyingoperation 302 of FIG. 3 may include an operation 446 for identifying theone or more relevant reported aspects including two or more relevantreported aspects associated with two or more source users as depicted inFIG. 4 h. For instance, the relevant reported aspect identificationmodule 102 of the computing device 10 identifying the one or morerelevant reported aspects 14 including two or more relevant reportedaspects 14 associated with two or more source users 2*.

In the same or different implementations, the relevant reported aspectidentifying operation 302 may include an operation 447 for identifyingthe one or more relevant reported aspects including one or more relevantreported aspects indicating one or more intermediate outcomes associatedwith the one or more target outcomes as depicted in FIG. 4 h. Forinstance, the relevant reported aspect identification module 102 of thecomputing device 10 identifying the one or more relevant reportedaspects 14 including one or more relevant reported aspects 14 indicatingone or more intermediate outcomes (e.g., running a mile in 10 minutes)associated with the one or more target outcomes (e.g., running a mile in7 minutes).

In the same or different implementations, the relevant reported aspectidentifying operation 302 may include an operation 448 for identifyingthe one or more relevant reported aspects in response to reception ofthe one or more solicitations via at least one of a wireless network anda wired network as depicted in FIG. 4 h. For instance, the relevantreported aspect identification module 102 of the computing device 10identifying the one or more relevant reported aspects 14 in response toreception of the one or more solicitations 13 (e.g., as received by thesolicitation reception module 122) via at least one of a wirelessnetwork and a wired network 50.

In various implementations, operation 448 may in turn include one ormore additional operations. For example, in some implementations,operation 448 may include an operation 449 for identifying the one ormore relevant reported aspects in response to reception of the one ormore solicitations from one or more network servers as depicted in FIG.4 h. For instance, the relevant reported aspect identification module102 of the computing device 10 identifying the one or more relevantreported aspects 14 in response to reception of the one or moresolicitations 13 from one or more network servers 60.

In the same or different implementations, operation 448 may include anoperation 450 for identifying the one or more relevant reported aspectsin response to reception of the one or more solicitations from one ormore local end user devices as depicted in FIG. 4 h. For instance, therelevant reported aspect identification module 102 of the computingdevice 10 identifying the one or more relevant reported aspects 14 inresponse to, for example, the solicitation reception module 122receiving the one or more solicitations 13 from one or more local enduser devices 30*.

In the same or different implementations, operation 448 may include anoperation 451 for identifying the one or more relevant reported aspectsin response to reception of the one or more solicitations from one ormore local source user devices as depicted in FIG. 4 h. For instance,the relevant reported aspect identification module 102 of the computingdevice 10 identifying the one or more relevant reported aspects 14 inresponse to reception of the one or more solicitations 13 from one ormore local source user devices 20*.

Referring back to the relevant reported aspect providing operation 304of FIG. 3, in various implementations, the relevant reported aspectproviding operation 304 may include one or more additional operations.For example, in some implementations, the relevant reported aspectproviding operation 304 may include an operation 552 for transmittingthe one or more relevant reported aspects via at least one of a wirelessnetwork and a wired network as depicted in FIG. 5 a. For instance, thenetwork transmission module 220 (see FIG. 2 b) of the computing device10 transmitting the one or more relevant reported aspects 14 via atleast one of a wireless network and a wired network 50.

In some implementations, operation 552 may further include an operation553 for transmitting the one or more relevant reported aspects to one ormore network devices as depicted in FIG. 5 a. For instance, the networkdevice transmission module 222 (see FIG. 2 b) of the computing device 10transmitting the one or more relevant reported aspects 14 to one or morenetwork devices (e.g., network servers, client devices, and so forth).

Operation 553 may, in turn, include one or more additional operations.For example, in some implementations, operation 553 may include anoperation 554 for transmitting the one or more relevant reported aspectsto one or more network servers as depicted in FIG. 5 a. For instance,the network device transmission module 222 of the computing device 10transmitting the one or more relevant reported aspects 14 to one or morenetwork servers 60.

In the same or different implementations, operation 553 may include anoperation 555 for transmitting the one or more relevant reported aspectsto one or more local end user devices as depicted in FIG. 5 a. Forinstance, the network device transmission module 222 of the computingdevice 10 transmitting the one or more relevant reported aspects 14 toone or more local end user devices 30*.

In the same or different implementations, operation 553 may include anoperation 556 for transmitting the one or more relevant reported aspectsto one or more local source user devices as depicted in FIG. 5 a. Forinstance, the network device transmission module 222 of the computingdevice 10 transmitting the one or more relevant reported aspects 14 toone or more local source user devices 20*.

In various implementations, the relevant reported aspect providingoperation 304 of FIG. 3 may include an operation 557 for providing aplurality of relevant reported aspects as depicted in FIG. 5 b. Forinstance, the relevant reported aspect providing module 104 of thecomputing device 10 providing a plurality of relevant reported aspects14 (e.g., providing two or more relevant reported aspects 14 via userinterface 120 and/or via network interface 118).

Operation 557 may, in turn, include an operation 558 for providing oneor more indications that link together two or more of the relevantreported aspects as depicted in FIG. 5 b. For instance, the linkindication providing module 224 (see FIG. 2 b) of the computing device10 providing one or more indications that link together two or more ofthe relevant reported aspects 14. For example, each of the two or morerelevant reported aspects 14 may be provided with attributes thatindicate that each of the two or more relevant reported aspects 14 areassociated with the same source user 2*.

Thus, in some implementations, operation 558 may further include anoperation 559 for providing the one or more indications that linktogether two or more of the relevant reported aspects by providing oneor more indications that indicate that each of the two or more of therelevant reported aspects is associated with a common source user asdepicted in FIG. 5 b. For instance, the link indication providing module224 (see FIG. 2 b) of the computing device 10 providing the one or moreindications that link together two or more of the relevant reportedaspects 14 by providing one or more indications that indicate that eachof the two or more of the relevant reported aspects 14 is associatedwith a common source user 2*.

In the same or different implementations, operation 558 may furtherinclude an operation 560 for providing one or more indications thatindicate one or more temporal relationships between the two or more ofthe relevant reported aspects as depicted in FIG. 5 b. For instance, therelationship indication providing module 226 (see FIG. 2 b) of thecomputing device 10 providing one or more indications that indicate oneor more temporal relationships between the two or more of the relevantreported aspects 14.

In the same or different implementations, operation 558 may furtherinclude an operation 561 for providing one or more indications thatindicate one or more specific time relationships between the two or moreof the relevant reported aspects as depicted in FIG. 5 b. For instance,the relationship indication providing module 226 of the computing device10 providing one or more indications that indicate one or more specifictime relationships between the two or more of the relevant reportedaspects 14.

In the same or different implementations, operation 558 may furtherinclude an operation 562 for providing one or more indications thatindicate one or more spatial relationships between the two or more ofthe relevant reported aspects as depicted in FIG. 5 b. For instance, therelationship indication providing module 226 of the computing device 10providing one or more indications that indicate one or more spatialrelationships between the two or more of the relevant reported aspects14.

In various implementations, operation 557 may include an operation 563for providing one or more relevant reported aspects that areintermediate outcomes associated with the one or more target outcomes asdepicted in FIG. 5 b. For instance, the relevant reported aspectproviding module 104 of the computing device 10 providing one or morerelevant reported aspects 14 that are intermediate outcomes associatedwith the one or more target outcomes.

Turning now to FIG. 6, which is a high-level block diagram illustratinga particular implementation of the computing device 10 of FIG. 1 b. Asillustrated, the computing device 10 may include a processor 602 (e.g.,microprocessor, controller, and so forth) coupled to storage medium 606(e.g., volatile or non-volatile memory). The storage medium 606 maystore computer readable instructions 604 (e.g., computer programproduct). The processor 602, in various implementations, may execute thecomputer readable instructions 604 in order to execute one or moreoperations described above and as illustrated in FIGS. 3, 4 a, 4 b, 4 c,4 d, 4 e, 4 f, 4 g, 4 h, 5 a, and 5 b.

For example, the processor 602 may execute the computer readableinstructions 604 in order to identify, in response to reception of oneor more solicitations 13, one or more relevant reported aspects 14associated with one or more source users 2* that are relevant toachieving one or more target outcomes, the identification of the one ormore relevant reported aspects 14 being based, at least in part, onrelevancy of the one or more relevant reported aspects 14 with respectto the one or more target outcomes; and/or to provide the one or morerelevant reported aspects 14 as illustrated by the operational flow 300of FIG. 3.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware and software implementations of aspects of systems; theuse of hardware or software is generally (but not always, in that incertain contexts the choice between hardware and software can becomesignificant) a design choice representing cost vs. efficiency tradeoffs.Those having skill in the art will appreciate that there are variousvehicles by which processes and/or systems and/or other technologiesdescribed herein can be effected (e.g., hardware, software, and/orfirmware), and that the preferred vehicle will vary with the context inwhich the processes and/or systems and/or other technologies aredeployed. For example, if an implementer determines that speed andaccuracy are paramount, the implementer may opt for a mainly hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a mainly software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes and/or devices and/or other technologies describedherein may be effected, none of which is inherently superior to theother in that any vehicle to be utilized is a choice dependent upon thecontext in which the vehicle will be deployed and the specific concerns(e.g., speed, flexibility, or predictability) of the implementer, any ofwhich may vary. Those skilled in the art will recognize that opticalaspects of implementations will typically employ optically-orientedhardware, software, and or firmware.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuitry (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuitry, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link, etc.).

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orany combination thereof can be viewed as being composed of various typesof “electrical circuitry.” Consequently, as used herein “electricalcircuitry” includes, but is not limited to, electrical circuitry havingat least one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of randomaccess memory), and/or electrical circuitry forming a communicationsdevice (e.g., a modem, communications switch, or optical-electricalequipment). Those having skill in the art will recognize that thesubject matter described herein may be implemented in an analog ordigital fashion or some combination thereof.

Those having skill in the art will recognize that it is common withinthe art to describe devices and/or processes in the fashion set forthherein, and thereafter use engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, at least a portion of the devices and/or processes described hereincan be integrated into a data processing system via a reasonable amountof experimentation. Those having skill in the art will recognize that atypical data processing system generally includes one or more of asystem unit housing, a video display device, a memory such as volatileand non-volatile memory, processors such as microprocessors and digitalsignal processors, computational entities such as operating systems,drivers, graphical user interfaces, and applications programs, one ormore interaction devices, such as a touch pad or screen, and/or controlsystems including feedback loops and control motors (e.g., feedback forsensing position and/or velocity; control motors for moving and/oradjusting components and/or quantities). A typical data processingsystem may be implemented utilizing any suitable commercially availablecomponents, such as those typically found in datacomputing/communication and/or network computing/communication systems.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures can beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled”, to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable”, to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents and/or wirelessly interactable and/or wirelessly interactingcomponents and/or logically interacting and/or logically interactablecomponents.

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.Furthermore, it is to be understood that the invention is defined by theappended claims.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to inventions containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.).

In those instances where a convention analogous to “at least one of A,B, or C, etc.” is used, in general such a construction is intended inthe sense one having skill in the art would understand the convention(e.g., “a system having at least one of A, B, or C” would include butnot be limited to systems that have A alone, B alone, C alone, A and Btogether, A and C together, B and C together, and/or A, B, and Ctogether, etc.). It will be further understood by those within the artthat virtually any disjunctive word and/or phrase presenting two or morealternative terms, whether in the description, claims, or drawings,should be understood to contemplate the possibilities of including oneof the terms, either of the terms, or both terms. For example, thephrase “A or B” will be understood to include the possibilities of “A”or “B” or “A and B.”

1.-129. (canceled)
 130. A system, comprising: a relevant reported aspectidentification module configured to identify one or more relevantreported aspects associated with one or more source users that arerelevant to achieving one or more target outcomes, the identification ofthe one or more relevant reported aspects being in response to receptionof one or more solicitations and being based, at least in part, onrelevancy of the one or more relevant reported aspects with respect toachieving the one or more target outcomes; and a relevant reportedaspect providing module configured to provide the identified one or morerelevant reported aspects. 131.-132. (canceled)
 133. The system of claim130, wherein said relevant reported aspect identification module,comprises: a relevant reported aspect identification module configuredto identify, in response to reception of one or more solicitations thatindicate one or more source users who have achieved the one or moretarget outcomes, the one or more relevant reported aspects.
 134. Thesystem of claim 130, wherein said relevant reported aspectidentification module, comprises: a relevant reported aspectidentification module configured to identify, in response to receptionof one or more solicitations that indicate the one or more targetoutcomes, the one or more relevant reported aspects.
 135. (canceled)136. The system of claim 134, wherein said relevant reported aspectidentification module, comprises: a relevant reported aspectidentification module configured to identify, in response to receptionof one or more solicitations that indicate the one or more targetoutcomes and that indicate one or more relevancy factors, the one ormore relevant reported aspects.
 137. The system of claim 136, whereinsaid relevant reported aspect identification module, comprises: arelevant reported aspect identification module configured to identify,in response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more aspect typesthat are of interest to one or more end users who are beneficiaries ofthe providing of the one or more relevant reported aspects, the one ormore relevant reported aspects.
 138. The system of claim 136, whereinsaid relevant reported aspect identification module, comprises: arelevant reported aspect identification module configured to identify,in response to reception of one or more solicitations that indicate theone or more target outcomes and that indicate one or more aspect typesindicated by at least one source user as being relevant to theachievement of the one or more target outcomes, the one or more relevantreported aspects.
 139. (canceled)
 140. The system of claim 136, whereinsaid relevant reported aspect identification module, comprises: arelevant reported aspect identification module configured to identifythe one or more relevant reported aspects in response to reception ofone or more solicitations that indicate the one or more target outcomesand that indicate one or more predefined time increments, the one ormore predefined time increments to be considered in order to determinerelevancy of one or more reported aspects with respect to achieving theone or more target outcomes.
 141. (canceled)
 142. The system of claim130, wherein said relevant reported aspect identification module,comprises: a source user associated reported aspect identificationmodule configured to identify one or more reported aspects that areassociated with the one or more source users, the one or more sourceusers having achieved the one or more target outcomes.
 143. The systemof claim 142, wherein said source user associated reported aspectidentification module, comprises: a target outcome correspondingreported aspect identification module configured to identify one or morereported aspects that correspond to the one or more target outcomes.144. The system of claim 143, wherein said source user associatedreported aspect identification module, comprises: an associated sourceuser determination module configured to determine one or more sourceusers who are associated with the one or more reported aspects thatcorrespond to the one or more target outcomes.
 145. The system of claim144, wherein said relevant reported aspect identification module,comprises: a relevant reported aspect identification module configuredto identify one or more reported aspects that are associated with theone or more source users determined to be associated with the one ormore reported aspects that correspond to the one or more targetoutcomes.
 146. The system of claim 145, wherein said relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects that are relevant with respect to one or more relevancyfactors from the one or more reported aspects that are associated withthe one or more source users determined to be associated with the one ormore reported aspects that correspond to the one or more targetoutcomes.
 147. The system of claim 146, wherein said relevancy factorrelevant reported aspect identification module, comprises: a relevancyfactor relevant reported aspect identification module configured toidentify one or more reported aspects that belong to one or more aspecttypes that are of interest to an end user who is a beneficiary of theone or more relevant reported aspects to be provided.
 148. The system ofclaim 146, wherein said relevancy factor relevant reported aspectidentification module, comprises: a relevancy factor relevant reportedaspect identification module configured to identify one or more reportedaspects that belong to one or more aspect types that have been indicatedby at least one source user as being relevant to the achievement of theone or more target outcomes.
 149. The system of claim 146, wherein saidrelevancy factor relevant reported aspect identification module,comprises: a relevancy factor relevant reported aspect identificationmodule configured to identify one or more reported aspects that belongto one or more aspect types that have been indicated by at least onethird party source as being relevant to the achievement of the one ormore target outcomes.
 150. The system of claim 146, wherein saidrelevancy factor relevant reported aspect identification module,comprises: a relevancy factor relevant reported aspect identificationmodule configured to identify one or more reported aspects that indicateone or more aspects that occurred within one or more predefined timeincrements, respectively, from one or more occurrences of the one ormore reported aspects that correspond to the one or more targetoutcomes.
 151. (canceled)
 152. The system of claim 130, wherein saidrelevant reported aspect identification module, comprises: a relevancyfactor relevant reported aspect identification module configured toidentify one or more reported aspects that are relevant to achieving theone or more target outcomes based on one or more relevancy factors. 153.The system of claim 152, wherein said relevancy factor relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects associated with one or more source users who share oneor more common traits with an end user, the end user being a beneficiaryof the one or more relevant reported aspects to be provided.
 154. Thesystem of claim 153, wherein said relevancy factor relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects associated with one or more source users who aremembers of one or more social networking groups that are associated withthe end user.
 155. The system of claim 153, wherein said relevancyfactor relevant reported aspect identification module, comprises: arelevancy factor relevant reported aspect identification moduleconfigured to identify one or more reported aspects associated with oneor more source users who are members of one or more ethnic or religiousgroups that are associated with the end user.
 156. The system of claim153, wherein said relevancy factor relevant reported aspectidentification module, comprises: a relevancy factor relevant reportedaspect identification module configured to identify one or more reportedaspects associated with one or more source users who are members of atleast one of a gender and an age group that is associated with the enduser.
 157. The system of claim 153, wherein said relevancy factorrelevant reported aspect identification module, comprises: a relevancyfactor relevant reported aspect identification module configured toidentify one or more reported aspects associated with one or more sourceusers who have one or more physical or mental handicaps that areassociated with the end user.
 158. The system of claim 153, wherein saidrelevancy factor relevant reported aspect identification module,comprises: a relevancy factor relevant reported aspect identificationmodule configured to identify one or more reported aspects associatedwith one or more source users who are associated with one or more healthor medical states that are further associated with the end user. 159.The system of claim 153, wherein said relevancy factor relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects associated with one or more source users who areassociated with one or more intellectual or academic states that arefurther associated with the end user.
 160. The system of claim 153,wherein said relevancy factor relevant reported aspect identificationmodule, comprises: a relevancy factor relevant reported aspectidentification module configured to identify one or more reportedaspects associated with one or more source users who are associated withone or more social states that are further associated with the end user.161. The system of claim 153, wherein said relevancy factor relevantreported aspect identification module, comprises: a relevancy factorrelevant reported aspect identification module configured to identifyone or more reported aspects associated with one or more source userswho are associated with one or more spiritual, political, or socialbeliefs that are further associated with the end user.
 162. The systemof claim 152, wherein said relevancy factor relevant reported aspectidentification module, comprises: a relevancy factor relevant reportedaspect identification module configured to identify one or more reportedaspects that indicate one or more behavior incidences associated withthe one or more source users.
 163. The system of claim 162, wherein saidrelevancy factor relevant reported aspect identification module,comprises: a relevancy factor relevant reported aspect identificationmodule configured to identify one or more reported aspects that indicateone or more incidences of activities executed by the one or more sourceusers.
 164. The system of claim 162, wherein said relevancy factorrelevant reported aspect identification module, comprises: a relevancyfactor relevant reported aspect identification module configured toidentify one or more reported aspects that indicate one or more userattitudes or conduct associated with the one or more source users. 165.The system of claim 152, wherein said relevancy factor relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects that indicate one or more incidences of one or moreuser beliefs associated with the one or more source users.
 166. Thesystem of claim 152, wherein said relevancy factor relevant reportedaspect identification module, comprises: a relevancy factor relevantreported aspect identification module configured to identify one or morereported aspects that indicate one or more incidences of one or moresubjective user states associated with the one or more source users.167. The system of claim 152, wherein said relevancy factor relevantreported aspect identification module, comprises: a relevancy factorrelevant reported aspect identification module configured to identifyone or more reported aspects that indicate one or more incidences of oneor more user physical characteristics associated with the one or moresource users.
 168. The system of claim 152, wherein said relevancyfactor relevant reported aspect identification module, comprises: arelevancy factor relevant reported aspect identification moduleconfigured to identify one or more reported aspects that indicate one ormore incidences of user locations associated with the one or more sourceusers.
 169. The system of claim 152, wherein said relevancy factorrelevant reported aspect identification module, comprises: a relevancyfactor relevant reported aspect identification module configured toidentify one or more reported aspects that indicate one or moreincidences of external events associated with the one or more sourceusers.
 170. The system of claim 130, wherein said relevant reportedaspect identification module, comprises: a log entry originated relevantreported aspect identification module configured to identify one or morereported aspects that were originally reported through log entries inorder to identify the one or more relevant reported aspects.
 171. Thesystem of claim 170, wherein said log entry originated relevant reportedaspect identification module, comprises: a log entry originated relevantreported aspect identification module configured to identify one or morereported aspects that were originally reported through blog entries inorder to identify the one or more relevant reported aspects.
 172. Thesystem of claim 170, wherein said log entry originated relevant reportedaspect identification module, comprises: a log entry originated relevantreported aspect identification module configured to identify one or morereported aspects that were originally reported through status reports inorder to identify the one or more relevant reported aspects. 173.(canceled)
 174. The system of claim 170, wherein said log entryoriginated relevant reported aspect identification module, comprises: alog entry originated relevant reported aspect identification moduleconfigured to identify one or more reported aspects that were originallyreported through sensing device entries in order to identify the one ormore relevant reported aspects.
 175. The system of claim 130, whereinsaid relevant reported aspect identification module, comprises: arelevant reported aspect identification module configured to identifytwo or more relevant reported aspects associated with two or more sourceusers.
 176. The system of claim 130, wherein said relevant reportedaspect identification module, comprises: a relevant reported aspectidentification module configured to identify one or more relevantreported aspects indicating one or more intermediate outcomes associatedwith the one or more target outcomes. 177.-180. (canceled)
 181. Thesystem of claim 130, wherein said relevant reported aspect providingmodule, comprises: a network transmission module configured to transmit,via at least one of a wireless network and a wired network, the one ormore relevant reported aspects. 182.-185. (canceled)
 186. The system ofclaim 130, wherein said relevant reported aspect providing module,comprises: a relevant reported aspect providing module configured toprovide a plurality of relevant reported aspects.
 187. The system ofclaim 186, wherein said relevant reported aspect providing module,comprises: a link indication providing module configured to provide oneor more indications that link together two or more of the relevantreported aspects.
 188. The system of claim 187, wherein said linkindication providing module, comprises: a link indication providingmodule configured to provide one or more indications that indicate thateach of the two or more of the relevant reported aspects is associatedwith a common source user.
 189. The system of claim 187, wherein saidlink indication providing module, comprises: a relationship indicationproviding module configured to provide one or more indications thatindicate one or more temporal relationships between the two or more ofthe relevant reported aspects.
 190. The system of claim 187, whereinsaid link indication providing module, comprises: a relationshipindication providing module configured to provide one or moreindications that indicate one or more specific time relationshipsbetween the two or more of the relevant reported aspects. 191.-192.(canceled)